Skip to content

docs(item): add routing section explaining how routerLink works#4456

Merged
ShaneK merged 2 commits intomajor-9.0from
v9/item-routing
Mar 31, 2026
Merged

docs(item): add routing section explaining how routerLink works#4456
ShaneK merged 2 commits intomajor-9.0from
v9/item-routing

Conversation

@ShaneK
Copy link
Copy Markdown
Member

@ShaneK ShaneK commented Mar 30, 2026

Resolves #1852

Description

Add a "Routing" section to the ion-item docs that explains how routerLink works across all four frameworks. Also updates the "Clickable Items" description to include routerLink alongside href and button.

Change Type

  • Fix
  • Feature
  • Refactor
  • Breaking Change
  • Documentation

Rationale / Problems Fixed

The ion-item docs had no section explaining how to use routerLink for client-side navigation, despite it being a core pattern. Developers had to piece together the behavior from scattered references across the routing and navigation guides. This adds framework-specific examples directly to the component page where users look first.

Preview

ion-item - Routing

@ShaneK ShaneK requested a review from a team as a code owner March 30, 2026 13:10
@ShaneK ShaneK requested review from thetaPC and removed request for a team March 30, 2026 13:10
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ionic-docs Ready Ready Preview, Comment Mar 31, 2026 4:22pm

Request Review

Copy link
Copy Markdown

@OS-jacobbell OS-jacobbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ShaneK ShaneK merged commit ba23835 into major-9.0 Mar 31, 2026
4 checks passed
@ShaneK ShaneK deleted the v9/item-routing branch March 31, 2026 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants